What does this PR do?

This PR implements a new type system for xlang serialization between java and python.

The changes includes:

• Refine type system spec: added new types:
  • named_enum: an enum whose value will be serialized as the registered name.
  • struct: a morphic(final) type serialized by Fury Struct serializer.
  • polymorphic_struct: a type which is not morphic(not final). i.e. it don't have subclasses. Suppose we're deserializing
    List<SomeClass>, we can save dynamic serializer dispatch if SomeClass is morphic(final).
  • compatible_struct: a morphic(final) type serialized by Fury compatible Struct serializer.
  • polymorphic_compatible_struct: a non-morphic(non-final) type serialized by Fury compatible Struct serializer.
  • named_struct: a struct whose type mapping will be encoded as a name.
  • named_polymorphic_struct: a polymorphic_struct whose type mapping will be encoded as a name.
  • named_compatible_struct: a compatible_struct whose type mapping will be encoded as a name.
  • named_polymorphic_compatible_struct: a polymorphic_compatible_struct whose type mapping will be encoded as a name.
  • ext: a type which will be serialized by a customized serializer.
  • polymorphic_ext: an ext type which is not morphic(not final).
  • named_ext: an ext type whose type mapping will be encoded as a name.
  • named_polymorphic_ext: an polymorphic_ext type whose type mapping will be encoded as a name.
• Added a new XtypeResolver in java to resolve xlang types
• Support register class mapping by id. Before this PR, we only support register class by name, which is more expensive at space/performance cost.
• Support pass type into to resolve type ambiguation such as ArrayList/Object[] in java. Users can serialize(List.of(1, 2, ,3)) and deserialize it into array by deserialize(bytes, Integer[].class)
• Refactor pyfury serialization by moving type resolver into python code from cython, this will make debug more easy and reduce code duplciation, it also speed serialization performance.
• golang xtype serialization test are disabled, it will be reenabled after new type system is implemented in golang

Related issues

Does this PR introduce any user-facing change?

• Does this PR introduce any public API change?
• Does this PR introduce any binary protocol compatibility change?

Benchmark